Skip to main content

Datavolo Cloud

Our cloud native SaaS, compromised of a Datavolo-managed Control Plane and either a Datavolo-managed Data Plane or a Customer-managed Data Plane, deployed as a kubernetes Operator.

Disaster Recovery

The Datavolo Cloud Product executes within AWS’ Elastic Kubernetes Service (EKS) infrastructure to include PersistentVolumeClaim (PVC) usage for data resiliency. The EKS infrastructure ensures that the Datavolo Cloud Product will be durable and automatically restarted should a component stop executing. It further ensures that data will not be lost in the event a restart is automatically triggered.

A Disaster is defined as an event when the entire AWS EKS is unavailable or is disabled enough to not restart the Datavolo Cloud Product.

Datavolo will maintain backups of the Customer’s data flow that will be available for the manual DR effort that Datavolo Support will coordinate with Customer. Runtime data that is stored in the Content Repository, FlowFile Repository, and Provenance Repository, may be unrecoverable in the event of a Disaster. Additionally, uploaded NAR and other asset files, as well as sensitive parameters may be unrecoverable.

The Customer is responsible for maintaining backups of NAR files, all needed asset files, and sensitive parameters. These will be leveraged in the event of a DR effort led by Datavolo Support.